Channel access priority for nr-u data bearers

ABSTRACT

Wireless communication devices, systems, and methods related to mechanisms to aid a user equipment in determining the channel access priority (CAPC) to use for a data radio bearer (DRB) on the response link, such as uplink (UL), that includes multiple quality of service (QoS) flows for an UL transmission (such as for a configured grant UL transmission). The UE may receive a plurality of QoS flows in a common DRB from a base station. The UE may apply a rule to select a CAPC to apply for all QoS flows in the common DRB on an UL transmission. This rule may alternatively include the base station making the selection of the CAPC to apply and informing the UE of the selected CAPC for implementation. The UE may then apply the selected CAPC to the UL transmission.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/947,835, filed Aug. 19, 2020, which claims priority to and thebenefit of U.S. Provisional Patent Application No. 62/891,091, filedAug. 23, 2019, both of which are hereby incorporated by reference intheir entirety as if fully set forth below in their entirety and for allapplicable purposes.

TECHNICAL FIELD

This application relates to wireless communication systems, and moreparticularly to methods (and associated devices and systems) fordetermining the channel access priority (CAPC) to use for a data radiobearer (DRB) that includes multiple quality of service (QoS) flows.

INTRODUCTION

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be capable ofsupporting communication with multiple users by sharing available systemresources. A wireless multiple-access communications system may includea number of base stations (BSs), each simultaneously supportingcommunications for multiple communication devices, which may beotherwise known as user equipment (UE).

The channel access priority for a QoS flow may be determined by the QoSflow's QoS identifier (also referred to as “5G QoS identifier” or 5QI)based on a mapping. When a UE transmits data on uplink (e.g., on aconfigured grant), the UE multiplexes data from logical channels (LCH)depending on their priority into a medium access control (MAC) protocoldata unit (PDU). The access priority (also referred to as “ChannelAccess Priority” or CAPC) of a MAC PDU may be the lowest access priorityamong all the logical channels in the MAC PDU when it is transmitted ona configured grant. This priority determines parameters to be used inperforming Listen-Before-Talk (LBT) before transmitting on theconfigured grant.

However, problems arise when multiple QoS flows are permitted on a givendata radio bearer (DRB), instead of being restricted to a one-to-onemapping. For example, with a many-to-one mapping possible (i.e.,multiple QoS flows to one DRB), the UE may not know what CAPC to use forthe DRB on the uplink. Thus, there is a need to provide UEs with theability to determine the CAPC to use for a DRB which includes multipleQoS flows with potentially different CAPCs.

BRIEF SUMMARY OF SOME EXAMPLES

The following summarizes some aspects of the present disclosure toprovide a basic understanding of the discussed technology. This summaryis not an extensive overview of all contemplated features of thedisclosure and is intended neither to identify key or critical elementsof all aspects of the disclosure nor to delineate the scope of any orall aspects of the disclosure. Its sole purpose is to present someconcepts of one or more aspects of the disclosure in summary form as aprelude to the more detailed description that is presented later.

For example, in an aspect of the disclosure, a method of wirelesscommunication includes receiving, by a user equipment (UE) from a basestation (BS), a plurality of downlink data packets comprising acorresponding plurality of quality of service flows (QoS flows), eachthe plurality of QoS flows being mapped to a common data radio bearer(DRB). The method further includes selecting, by the UE, a channelaccess priority class (CAPC) for the common DRB for transmitting an ULdata packet based on a rule applied to the plurality of QoS flows mappedto the common DRB. The method further includes transmitting, by the UEto the BS, the uplink data packet with the selected CAPC.

In an additional aspect of the disclosure, a method of wirelesscommunication includes mapping, by a base station (BS), a plurality ofdownlink data packets comprising a corresponding plurality of quality ofservice flows (QoS flows) to a common data radio bearer (DRB). Themethod further includes transmitting, by the BS to a user equipment(UE), the plurality of downlink data packets on the common DRB. Themethod further includes receiving, by the BS from the UE, an uplink (UL)data packet on the common DRB having a channel access priority class(CAPC) selected based on a rule applied to the plurality of QoS flowsmapped to the common DRB.

In an additional aspect of the disclosure, a user equipment includes atransceiver configured to receive, from a base station (BS), a pluralityof downlink data packets comprising a corresponding plurality of qualityof service flows (QoS flows), each the plurality of QoS flows beingmapped to a common data radio bearer (DRB). The user equipment furtherincludes a processor configured to select a channel access priorityclass (CAPC) for the common DRB for transmitting an UL data packet basedon a rule applied to the plurality of QoS flows mapped to the commonDRB. The user equipment further includes wherein the transceiver isfurther configured to transmit, to the BS, the uplink data packet withthe selected CAPC.

In an additional aspect of the disclosure, a base station includes aprocessor configured to map a plurality of downlink data packetscomprising a corresponding plurality of quality of service flows (QoSflows) to a common data radio bearer (DRB). The base station furtherincludes a transceiver configured to transmit, to a user equipment (UE),the plurality of downlink data packets on the common DRB, and receive,from the UE, an uplink (UL) data packet on the common DRB having achannel access priority class (CAPC) selected based on a rule applied tothe plurality of QoS flows mapped to the common DRB.

In an additional aspect of the disclosure, a non-transitorycomputer-readable medium is provided having program code recordedthereon, the program code comprising code for causing a user equipment(UE) to receive, from a base station (BS), a plurality of downlink datapackets comprising a corresponding plurality of quality of service flows(QoS flows), each the plurality of QoS flows being mapped to a commondata radio bearer (DRB). The program code further comprises code forcausing the UE to select a channel access priority class (CAPC) for thecommon DRB for transmitting an UL data packet based on a rule applied tothe plurality of QoS flows mapped to the common DRB. The program codefurther comprises code for causing the UE to transmit, to the BS, theuplink data packet with the selected CAPC.

In an additional aspect of the disclosure, a non-transitorycomputer-readable medium is provided having program code recordedthereon, the program code comprising code for causing a base station(BS) to map a plurality of downlink data packets comprising acorresponding plurality of quality of service flows (QoS flows) to acommon data radio bearer (DRB). The program code further comprises codefor causing the BS to transmit, to a user equipment (UE), the pluralityof downlink data packets on the common DRB. The program code furthercomprises code for causing the BS to receive, from the UE, an uplink(UL) data packet on the common DRB having a channel access priorityclass (CAPC) selected based on a rule applied to the plurality of QoSflows mapped to the common DRB.

In an additional aspect of the disclosure, a user equipment includesmeans for receiving, by the user equipment (UE) from a base station(BS), a plurality of downlink data packets comprising a correspondingplurality of quality of service flows (QoS flows), each the plurality ofQoS flows being mapped to a common data radio bearer (DRB). The userequipment further comprises means for selecting a channel accesspriority class (CAPC) for the common DRB for transmitting an UL datapacket based on a rule applied to the plurality of QoS flows mapped tothe common DRB. The program code further comprises means fortransmitting, to the BS, the uplink data packet with the selected CAPC.

In an additional aspect of the disclosure, a base station includes meansfor mapping, by the base station (BS), a plurality of downlink datapackets comprising a corresponding plurality of quality of service flows(QoS flows) to a common data radio bearer (DRB). The base stationfurther includes means for transmitting, to a user equipment (UE), theplurality of downlink data packets on the common DRB. The program codefurther includes means for receiving, from the UE, an uplink (UL) datapacket on the common DRB having a channel access priority class (CAPC)selected based on a rule applied to the plurality of QoS flows mapped tothe common DRB.

Other aspects, features, and embodiments of the present invention willbecome apparent to those of ordinary skill in the art, upon reviewingthe following description of specific, exemplary embodiments of thepresent invention in conjunction with the accompanying figures. Whilefeatures of the present invention may be discussed relative to certainembodiments and figures below, all embodiments of the present inventioncan include one or more of the advantageous features discussed herein.In other words, while one or more embodiments may be discussed as havingcertain advantageous features, one or more of such features may also beused in accordance with the various embodiments of the inventiondiscussed herein. In similar fashion, while exemplary embodiments may bediscussed below as device, system, or method embodiments, it should beunderstood that such exemplary embodiments can be implemented in variousdevices, systems, and methods.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a wireless communication network according to someembodiments of the present disclosure.

FIG. 2 illustrates a protocol diagram of a wireless communication methodaccording to some embodiments of the present disclosure.

FIG. 3 is a block diagram of a user equipment (UE) according to someembodiments of the present disclosure.

FIG. 4 is a block diagram of an exemplary base station (BS) according toembodiments of the present disclosure.

FIG. 5 illustrates a wireless communication network interactionaccording to some embodiments of the present disclosure.

FIG. 6 illustrates a table format for a mapping relationship accordingto some embodiments of the present disclosure.

FIG. 7 illustrates a flow diagram of a wireless communication methodaccording to some embodiments of the present disclosure.

FIG. 8 illustrates a flow diagram of a wireless communication methodaccording to some embodiments of the present disclosure.

DETAILED DESCRIPTION

The detailed description set forth below, in connection with theappended drawings, is intended as a description of variousconfigurations and is not intended to represent the only configurationsin which the concepts described herein may be practiced. The detaileddescription includes specific details for the purpose of providing athorough understanding of the various concepts. However, it will beapparent to those skilled in the art that these concepts may bepracticed without these specific details. In some instances, well-knownstructures and components are shown in block diagram form in order toavoid obscuring such concepts.

This disclosure relates generally to wireless communications systems,also referred to as wireless communications networks. In variousembodiments, the techniques and apparatus may be used for wirelesscommunication networks such as code division multiple access (CDMA)networks, time division multiple access (TDMA) networks, frequencydivision multiple access (FDMA) networks, orthogonal FDMA (OFDMA)networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, GlobalSystem for Mobile Communications (GSM) networks, 5^(th) Generation (5G)or new radio (NR) networks, as well as other communications networks. Asdescribed herein, the terms “networks” and “systems” may be usedinterchangeably.

An OFDMA network may implement a radio technology such as evolved UTRA(E-UTRA), Institute of Electrical and Electronics Engineers (IEEE)802.11, IEEE 802.16, IEEE 802.20, flash-OFDM and the like. UTRA, E-UTRA,and GSM are part of universal mobile telecommunication system (UMTS). Inparticular, long term evolution (LTE) is a release of UMTS that usesE-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documentsprovided from an organization named “3rd Generation Partnership Project”(3GPP), and cdma2000 is described in documents from an organizationnamed “3rd Generation Partnership Project 2” (3GPP2). These variousradio technologies and standards are known or are being developed. Forexample, the 3rd Generation Partnership Project (3GPP) is acollaboration between groups of telecommunications associations thataims to define a globally applicable third generation (3G) mobile phonespecification. 3GPP long term evolution (LTE) is a 3GPP project whichwas aimed at improving the UMTS mobile phone standard. The 3GPP maydefine specifications for the next generation of mobile networks, mobilesystems, and mobile devices. The present disclosure is concerned withthe evolution of wireless technologies from LTE, 4G, 5G, NR, and beyondwith shared access to wireless spectrum between networks using acollection of new and different radio access technologies or radio airinterfaces.

In particular, 5G networks contemplate diverse deployments, diversespectrum, and diverse services and devices that may be implemented usingan OFDM-based unified, air interface. In order to achieve these goals,further enhancements to LTE and LTE-A are considered in addition todevelopment of the new radio technology for 5G NR networks. The 5G NRwill be capable of scaling to provide coverage (1) to a massive Internetof things (IoTs) with an ultra-high density (e.g., ˜1M nodes/km²),ultra-low complexity (e.g., ˜10s of bits/sec), ultra-low energy (e.g.,˜10+ years of battery life), and deep coverage with the capability toreach challenging locations; (2) including mission-critical control withstrong security to safeguard sensitive personal, financial, orclassified information, ultra-high reliability (e.g., ˜99.9999%reliability), ultra-low latency (e.g., ˜1 ms), and users with wideranges of mobility or lack thereof; and (3) with enhanced mobilebroadband including extreme high capacity (e.g., ˜10 Tbps/km²), extremedata rates (e.g., multi-Gbps rate, 100+ Mbps user experienced rates),and deep awareness with advanced discovery and optimizations.

The 5G NR may be implemented to use optimized OFDM-based waveforms withscalable numerology and transmission time interval (TTI); having acommon, flexible framework to efficiently multiplex services andfeatures with a dynamic, low-latency time division duplex(TDD)/frequency division duplex (FDD) design; and with advanced wirelesstechnologies, such as massive multiple input, multiple output (MIMO),robust millimeter wave (mmWave) transmissions, advanced channel coding,and device-centric mobility. Scalability of the numerology in 5G NR,with scaling of subcarrier spacing, may efficiently address operatingdiverse services across diverse spectrum and diverse deployments. Forexample, in various outdoor and macro coverage deployments of less than3 GHz FDD/TDD implementations, subcarrier spacing may occur with 15 kHz,for example over 5, 10, 20 MHz, and the like bandwidth (BW). For othervarious outdoor and small cell coverage deployments of TDD greater than3 GHz, subcarrier spacing may occur with 30 kHz over 80/100 MHz BW. Forother various indoor wideband implementations, using a TDD over theunlicensed portion of the 5 GHz band, the subcarrier spacing may occurwith 60 kHz over a 160 MHz BW. Finally, for various deploymentstransmitting with mmWave components at a TDD of 28 GHz, subcarrierspacing may occur with 120 kHz over a 500 MHz BW.

The scalable numerology of the 5G NR facilitates scalable TTI fordiverse latency and quality of service (QoS) requirements. For example,shorter TTI may be used for low latency and high reliability, whilelonger TTI may be used for higher spectral efficiency. The efficientmultiplexing of long and short TTIs to allow transmissions to start onsymbol boundaries. 5G NR also contemplates a self-contained integratedsubframe design with uplink/downlink scheduling information, data, andacknowledgement in the same subframe. The self-contained integratedsubframe supports communications in unlicensed or contention-basedshared spectrum, adaptive uplink/downlink that may be flexiblyconfigured on a per-cell basis to dynamically switch between uplink anddownlink to meet the current traffic needs.

Various other aspects and features of the disclosure are furtherdescribed below. It should be apparent that the teachings herein may beembodied in a wide variety of forms and that any specific structure,function, or both being disclosed herein is merely representative andnot limiting. Based on the teachings herein one of an ordinary level ofskill in the art should appreciate that an aspect disclosed herein maybe implemented independently of any other aspects and that two or moreof these aspects may be combined in various ways. For example, anapparatus may be implemented or a method may be practiced using anynumber of the aspects set forth herein. In addition, such an apparatusmay be implemented or such a method may be practiced using otherstructure, functionality, or structure and functionality in addition toor other than one or more of the aspects set forth herein. For example,a method may be implemented as part of a system, device, apparatus,and/or as instructions stored on a computer readable medium forexecution on a processor or computer. Furthermore, an aspect maycomprise at least one element of a claim.

The present application describes mechanisms to determine the channelaccess priority (CAPC) to use for a data radio bearer (DRB) thatincludes multiple quality of service (QoS) flows for an UL configuredgrant transmission.

In some embodiments, a BS and a UE may employ a rules-based approach todetermine what CAPC to use in a UL communication (e.g., during aconfigured grant transmission). The rules may be configured at the UEand the BS prior to a communication. For example, the UE may receive atransmission of data from the BS that includes multiple different QoSflows carried on a common DRB (also referred to herein as a logicalchannel, LCH). For example, the rule may be that different QoS flowscarried on a common DRB are mapped by the BS based on each QoS flow inthe common DRB having the same access priority. As another example, therule may be that the UE select the CAPC based on the lowest accesspriority of the QoS flows on the common DRB. As another example, therule may be that the UE select the CAPC based on the highest accesspriority of the QoS flows on the common DRB. As another example, therule may be that the UE select the CAPC based on the lowest or highestpriority from among a subset of QoS flows on the common DRB, where thesubset is signaled by the BS.

As another example, the rule may be that the UE select the CAPC based onthe priority of the greatest number of QoS flows on the common DRB thathave the same priority. As another example, the BS may determine theCAPC to use for the common DRB (or a value that is determinative ofCAPC) and signal that determination to the UE per the LCH, as well asupdated such as when one or more QoS flows are added or removed from theDRB. As another example, the BS may configure multiple mappings via RRCsignaling and dynamically change which mapping to use via MAC controlelement (CE), such as based on traffic patterns and traffic history ofthe QoS flows.

In some embodiments, the UE may receive one or more packets belonging toa QoS flow that the UE has not received in the common DRB. This mayrefer to reflective QoS. In such situations, the UE may update theaccess priority of the common DRB according to a known rule (such as oneof the above-noted rules). The UE may receive the CAPC for this new QoSflow, such as in the received packet, in the service data adaptationprotocol (SDAP) header, the packet data convergence protocol (PDCP)header, MAC CE, RRC signaling, or PDCP control PDU. This may instead, oradditionally, include the UE receiving the 5QI for this QoS flow, suchas in a received packet, or SDAP header, PDCP header, MAC CE, RRCsignaling, or PDCP control PDU. The CAPC for the common DRB may beupdated according to one or more of the above rules with this newinformation for the new QoS flow. Further, when the BS adds or removesQoS flows (one or multiple) for the common DRB, the UE may update theCAPC of the common DRB based on the rule(s) in effect (such as fromamong those discussed above). Further, whenever the CAPC changes withrespect to the common DRB for an UL transmission from the UE, the newCAPC may be applied to subsequent UL transmissions for the common DRB,or alternatively may begin application when received. In general, when anew QoS flow is added, or when an existing QoS flow is removed from acommon DRB, the CAPC may be signaled to the UE (or, alternatively to theCAPC, the 5QI for the QoS flow).

Aspects of the present application provide several benefits. Forexample, embodiments of the present disclosure enable UEs to determinewhat CAPC to apply to a common DRB on the uplink for a transmission(e.g., in configured grant scenarios or in dynamic grant scenarios),when the common DRB includes multiple QoS flows with potentiallydifferent 5QIs from each other. Additional features and benefits of thepresent disclosure are set forth in the following description.

FIG. 1 illustrates a wireless communication network 100 according tosome embodiments of the present disclosure. The network 100 may be a 5Gnetwork. The network 100 includes a number of base stations (BSs) 105(individually labeled as 105 a, 105 b, 105 c, 105 d, 105 e, and 105 f)and other network entities. ABS 105 may be a station that communicateswith UEs 115 and may also be referred to as an evolved node B (eNB), anext generation eNB (gNB), an access point, and the like. Each BS 105may provide communication coverage for a particular geographic area. In3GPP, the term “cell” may refer to this particular geographic coveragearea of a BS 105 and/or a BS subsystem serving the coverage area,depending on the context in which the term is used.

A BS 105 may provide communication coverage for a macro cell or a smallcell, such as a pico cell or a femto cell, and/or other types of cell. Amacro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and may allow unrestricted access by UEswith service subscriptions with the network provider. A small cell, suchas a pico cell, would generally cover a relatively smaller geographicarea and may allow unrestricted access by UEs with service subscriptionswith the network provider. A small cell, such as a femto cell, wouldalso generally cover a relatively small geographic area (e.g., a home)and, in addition to unrestricted access, may also provide restrictedaccess by UEs having an association with the femto cell (e.g., UEs in aclosed subscriber group (CSG), UEs for users in the home, and the like).A BS for a macro cell may be referred to as a macro BS. A BS for a smallcell may be referred to as a small cell BS, a pico BS, a femto BS or ahome BS. In the example shown in FIG. 1, the BSs 105 d and 105 e may beregular macro BSs, while the BSs 105 a-105 c may be macro BSs enabledwith one of three dimension (3D), full dimension (FD), or massive MIMO.The BSs 105 a-105 c may take advantage of their higher dimension MIMOcapabilities to exploit 3D beamforming in both elevation and azimuthbeamforming to increase coverage and capacity. The BS 105 f may be asmall cell BS which may be a home node or portable access point. A BS105 may support one or multiple (e.g., two, three, four, and the like)cells.

The network 100 may support synchronous or asynchronous operation. Forsynchronous operation, the BSs may have similar frame timing, andtransmissions from different BSs may be approximately aligned in time.For asynchronous operation, the BSs may have different frame timing, andtransmissions from different BSs may not be aligned in time.

The UEs 115 are dispersed throughout the wireless network 100, and eachUE 115 may be stationary or mobile. A UE 115 may also be referred to asa terminal, a mobile station, a subscriber unit, a station, or the like.A UE 115 may be a cellular phone, a personal digital assistant (PDA), awireless modem, a wireless communication device, a handheld device, atablet computer, a laptop computer, a cordless phone, a wireless localloop (WLL) station, or the like. In one aspect, a UE 115 may be a devicethat includes a Universal Integrated Circuit Card (UICC). In anotheraspect, a UE may be a device that does not include a UICC. In someaspects, the UEs 115 that do not include UICCs may also be referred toas IoT devices or internet of everything (IoE) devices. The UEs 115a-115 d are examples of mobile smart phone-type devices accessingnetwork 100. A UE 115 may also be a machine specifically configured forconnected communication, including machine type communication (MTC),enhanced MTC (eMTC), narrowband IoT (NB-IoT) and the like. The UEs 115e-115 k are examples of various machines configured for communicationthat access the network 100. A UE 115 may be able to communicate withany type of the BSs, whether macro BS, small cell, or the like. In FIG.1, a lightning bolt (e.g., communication links) indicates wirelesstransmissions between a UE 115 and a serving BS 105, which is a BSdesignated to serve the UE 115 on the downlink and/or uplink, or desiredtransmission between BSs, and backhaul transmissions between BSs.

In operation, the BSs 105 a-105 c may serve the UEs 115 a and 115 busing 3D beamforming and coordinated spatial techniques, such ascoordinated multipoint (CoMP) or multi-connectivity. The macro BS 105 dmay perform backhaul communications with the BSs 105 a-105 c, as well assmall cell, the BS 105 f. The macro BS 105 d may also transmitsmulticast services which are subscribed to and received by the UEs 115 cand 115 d. Such multicast services may include mobile television orstream video, or may include other services for providing communityinformation, such as weather emergencies or alerts, such as Amber alertsor gray alerts.

The BSs 105 may also communicate with a core network. The core networkmay provide user authentication, access authorization, tracking,Internet Protocol (IP) connectivity, and other access, routing, ormobility functions. At least some of the BSs 105 (e.g., which may be anexample of a gNB or an access node controller (ANC)) may interface withthe core network through backhaul links (e.g., NG-C, NG-U, etc.) and mayperform radio configuration and scheduling for communication with theUEs 115. In various examples, the BSs 105 may communicate, eitherdirectly or indirectly (e.g., through core network), with each otherover backhaul links (e.g., X1, X2, etc.), which may be wired or wirelesscommunication links.

The network 100 may also support mission critical communications withultra-reliable and redundant links for mission critical devices, such asthe UE 115 e, which may be a drone. Redundant communication links withthe UE 115 e may include links from the macro BSs 105 d and 105 e, aswell as links from the small cell BS 105 f. Other machine type devices,such as the UE 115 f (e.g., a thermometer), the UE 115 g (e.g., smartmeter), and UE 115 h (e.g., wearable device) may communicate through thenetwork 100 either directly with BSs, such as the small cell BS 105 f,and the macro BS 105 e, or in multi-hop configurations by communicatingwith another user device which relays its information to the network,such as the UE 115 f communicating temperature measurement informationto the smart meter, the UE 115 g, which is then reported to the networkthrough the small cell BS 105 f. The network 100 may also provideadditional network efficiency through dynamic, low-latency TDD/FDDcommunications, such as in a vehicle-to-vehicle (V2V) communication.

In some implementations, the network 100 utilizes OFDM-based waveformsfor communications. An OFDM-based system may partition the system BWinto multiple (K) orthogonal subcarriers, which are also commonlyreferred to as subcarriers, tones, bins, or the like. Each subcarriermay be modulated with data. In some instances, the subcarrier spacingbetween adjacent subcarriers may be fixed, and the total number ofsubcarriers (K) may be dependent on the system BW. The system BW mayalso be partitioned into subbands. In other instances, the subcarrierspacing and/or the duration of TTIs may be scalable.

In an embodiment, the BSs 105 may assign or schedule transmissionresources (e.g., in the form of time-frequency resource blocks (RB)) fordownlink (DL) and uplink (UL) transmissions in the network 100. DLrefers to the transmission direction from a BS 105 to a UE 115, whereasUL refers to the transmission direction from a UE 115 to a BS 105. Thecommunication may be in the form of radio frames. A radio frame may bedivided into a plurality of subframes or slots, for example, about 10.Each slot may be further divided into mini-slots. In a FDD mode,simultaneous UL and DL transmissions may occur in different frequencybands. For example, each subframe includes a UL subframe in a ULfrequency band and a DL subframe in a DL frequency band. In a TDD mode,UL and DL transmissions occur at different time periods using the samefrequency band. For example, a subset of the subframes (e.g., DLsubframes) in a radio frame may be used for DL transmissions and anothersubset of the subframes (e.g., UL subframes) in the radio frame may beused for UL transmissions.

The DL subframes and the UL subframes may be further divided intoseveral regions. For example, each DL or UL subframe may havepre-defined regions for transmissions of reference signals, controlinformation, and data. Reference signals are predetermined signals thatfacilitate the communications between the BSs 105 and the UEs 115. Forexample, a reference signal may have a particular pilot pattern orstructure, where pilot tones may span across an operational BW orfrequency band, each positioned at a pre-defined time and a pre-definedfrequency. For example, a BS 105 may transmit cell specific referencesignals (CRSs) and/or channel state information—reference signals(CSI-RSs) to enable a UE 115 to estimate a DL channel. Similarly, a UE115 may transmit sounding reference signals (SRSs) to enable a BS 105 toestimate a UL channel Control information may include resourceassignments and protocol controls. Data may include protocol data and/oroperational data. In some embodiments, the BSs 105 and the UEs 115 maycommunicate using self-contained subframes. A self-contained subframemay include a portion for DL communication and a portion for ULcommunication. A self-contained subframe may be DL-centric orUL-centric. A DL-centric subframe may include a longer duration for DLcommunication than for UL communication. A UL-centric subframe mayinclude a longer duration for UL communication than for ULcommunication.

In an embodiment, the network 100 may be an NR network deployed over alicensed spectrum. The BSs 105 may transmit synchronization signals(e.g., including a primary synchronization signal (PSS) and a secondarysynchronization signal (SSS)) in the network 100 to facilitatesynchronization. The BSs 105 may broadcast system information associatedwith the network 100 (e.g., including a master information block (MIB),remaining system information (RMSI), and other system information (OSI))to facilitate initial network access. In some instances, the BSs 105 maybroadcast the PSS, the SSS, and/or the MIB in the form ofsynchronization signal block (SSBs) over a physical broadcast channel(PBCH) and may broadcast the RMSI and/or the OSI over a physicaldownlink shared channel (PDSCH).

In an embodiment, a UE 115 attempting to access the network 100 mayperform an initial cell search by detecting a PSS from a BS 105. The PSSmay enable synchronization of period timing and may indicate a physicallayer identity value. The UE 115 may then receive a SSS. The SSS mayenable radio frame synchronization, and may provide a cell identityvalue, which may be combined with the physical layer identity value toidentify the cell. The PSS and the SSS may be located in a centralportion of a carrier or any suitable frequencies within the carrier.

After receiving the PSS and SSS, the UE 115 may receive a MIB. The MIBmay include system information for initial network access and schedulinginformation for RMSI and/or OSI. After decoding the MIB, the UE 115 mayreceive RMSI and/or OSI. The RMSI and/or OSI may include radio resourcecontrol (RRC) information related to random access channel (RACH)procedures, paging, control resource set (CORESET) for physical downlinkcontrol channel (PDCCH) monitoring, physical uplink control channel(PUCCH), physical uplink shared channel (PUSCH), power control, and SRS.

After obtaining the MIB, the RMSI and/or the OSI, the UE 115 may performa random access procedure to establish a connection with the BS 105. Ina four-step random access procedure, the UE 115 may transmit a randomaccess preamble and the BS 105 may respond with a random accessresponse. The random access response (RAR) may include a detected randomaccess preamble identifier (ID) corresponding to the random accesspreamble, timing advance (TA) information, a UL grant, a temporarycell-radio network temporary identifier (C-RNTI), and/or a backoffindicator. Upon receiving the random access response, the UE 115 maytransmit a connection request to the BS 105 and the BS 105 may respondwith a connection response. The connection response may indicate acontention resolution. In some examples, the random access preamble, theRAR, the connection request, and the connection response may be referredto as a message 1 (MSG 1), a message 2 (MSG 2), a message 3 (MSG 3), anda message 4 (MSG 4), respectively. According to embodiments of thepresent disclosure, the random access procedure may be a two-step randomaccess procedure, where the UE 115 may transmit a random access preambleand a connection request in a single transmission and the BS 105 mayrespond by transmitting a random access response and a connectionresponse in a single transmission. The combined random access preambleand connection request in the two-step random access procedure may bereferred to as a message A (msgA). The combined random access responseand connection response in the two-step random access procedure may bereferred to as a message B (msgB).

After establishing a connection, the UE 115 and the BS 105 can enter anoperational state, where operational data may be exchanged. For example,the BS 105 may schedule the UE 115 for UL and/or DL communications. TheBS 105 may transmit UL and/or DL scheduling grants to the UE 115 via aPDCCH. The BS 105 may transmit a DL communication signal to the UE 115via a PDSCH according to a DL scheduling grant. The UE 115 may transmita UL communication signal to the BS 105 via a PUSCH and/or PUCCHaccording to a UL scheduling grant. Further, the UE 115 may transmit aUL communication signal to the BS 105 according to a configured grantscheme.

A configured grant transmission is an unscheduled transmission,performed on the channel without a UL grant. A configured grant ULtransmission may also be referred to as a grantless, grant-free, orautonomous transmission. In some examples, the UE 115 may transmit a ULresource via a configured grant. Additionally, configured-UL data mayalso be referred to as grantless UL data, grant-free UL data,unscheduled UL data, or autonomous UL (AUL) data. Additionally, aconfigured grant may also be referred to as a grant-free grant,unscheduled grant, or autonomous grant. The resources and otherparameters used by the UE for a configured grant transmission may beprovided by the BS in one or more of a RRC configuration or anactivation DCI, without an explicit grant for each UE transmission. TheCAPC informs the UE 115 with respect to parameters to be used inperforming Listen-Before-Talk (LBT) before transmitting on theconfigured grant resource (e.g., a higher CAPC having a shorter LBTtiming and a lower CAPC having a longer LBT timing due to lowerpriority). Challenges may arise when multiple QoS flows are permitted ona given data radio bearer (DRB), instead of a one-to-one mapping. With amany-to-one mapping possible, the UE may not be able to determine whatCAPC to use for a configured grant UL.

In some embodiments, the BS 105 and the UE 115 may employ a rules-basedapproach to determine what CAPC to use in an UL transmission, includingfor example a configured grant UL communication or a dynamic grant ULcommunication. The rules may be configured at the UE 115 and the BS 105prior to a communication. For example, the UE 115 may receive atransmission of data from the BS 105 that includes multiple differentQoS flows carried on a common DRB (also referred to herein as a logicalchannel, LCH).

For example, the rule may be that different QoS flows carried on acommon DRB are mapped by the BS 105 based on each QoS flow in the commonDRB having the same access priority (such as determined by the QoSflow's QoS identifier (5QI) at the BS 105). As another example, the rulemay be that the UE 115 select the CAPC based on the lowest accesspriority of the QoS flows on the common DRB. As another example, therule may be that the UE 115 select the CAPC based on the highest accesspriority of the QoS flows on the common DRB. As another example, therule may be that the UE 115 select the CAPC based on the lowest orhighest priority from among a subset of QoS flows on the common DRB,where the subset is signaled by the BS 105. As another example, the rulemay be that the UE 115 select the CAPC based on the priority of thegreatest number of QoS flows on the common DRB that have the samepriority. As another example, the BS 105 may determine the CAPC (or avalue that is determinative of CAPC) for the common DRB and signal thatdetermination to the UE 115 per the LCH, as well as updated such as whenone or more QoS flows are added or removed from the common DRB. Asanother example, the BS 105 may configure multiple mappings via RRCsignaling and dynamically change which mapping to use via MAC controlelement (CE), such as based on traffic patterns and traffic history ofthe QoS flows.

In some embodiments, the UE 115 may receive one or more packetsbelonging to a QoS flow that the UE 115 has not received in the commonDRB. This may refer to reflective QoS. In such situations, the UE 115may update the access priority of the common DRB according to a knownrule (such as one of the above-noted rules). The UE 115 may receive theCAPC for this new QoS flow, such as in the received packet, in theservice data adaptation protocol (SDAP) header, the packet dataconvergence protocol (PDCP) header, MAC CE, RRC signaling, or PDCPcontrol PDU. This may instead, or additionally, include the UE 115receiving the 5QI for this QoS flow, such as in a received packet, orSDAP header, PDCP header, MAC CE, RRC signaling, or PDCP control PDU.With this additional information for the new QoS flow, the CAPC for thecommon DRB may be updated according to one or more of the above rules.

Further, when the BS 105 adds or removes QoS flows (one or multiple) forthe common DRB, the UE 105 may update the CAPC of the common DRB basedon the rule(s) in effect (such as from among those discussed above).Further, whenever the CAPC changes with respect to the common DRB for anUL transmission from the UE 115, the new CAPC may be applied tosubsequent UL transmissions for the common DRB, or alternatively maybegin application when received. In general, when a new QoS flow isadded, or when an existing QoS flow is removed from a common DRB, theCAPC may be signaled to the UE 115 (or, alternatively to the CAPC, the5QI for the QoS flow).

As a result, embodiments of the present disclosure enable UEs 115 todetermine what CAPC to apply to a DRB on the uplink for a transmission(e.g., in configured grant scenarios or in dynamic grant scenarios),when the common DRB includes multiple QoS flows with potentiallydifferent 5QIs/access priorities determined from the 5QIs from eachother.

The network 100 may operate over a shared frequency band or anunlicensed frequency band, for example, at about 3.5 gigahertz (GHz),sub-6 GHz or higher frequencies in the mmWave band. The network 100 maypartition a frequency band into multiple channels, for example, eachoccupying about 20 megahertz (MHz). The BSs 105 and the UEs 115 may beoperated by multiple network operating entities sharing resources in theshared communication medium and may acquire channel occupancy time (COT)in the share medium for communications. A COT may be non-continuous intime and may refer to an amount of time a wireless node can send frameswhen it has won contention for the wireless medium. Each COT may includea plurality of transmission slots. A COT may also be referred to as atransmission opportunity (TXOP).

FIG. 2 illustrates a protocol diagram of a wireless communication method200, particularly a CAPC determination procedure, between a UE 115 and aBS 105 according to some embodiments of the present disclosure.

At action 202, the BS 105 receives QoS flows from the core networkgateway function and maps the QoS flows to a common DRB. For example,the QoS flows may correspond to packets that were filtered at the corenetwork level (e.g., user plane function, UPF) into the different QoSflows. There may be multiple DRBs between a BS 105 and a UE 115, and aone-to-many relationship between the QoS flows and a common DRB. Thus,though there may be multiple DRBs, and any number of QoS flows in any ofthem, discussion herein will describe exemplary cases with respect to agiven DRB with multiple QoS flows mapped to it for sake of discussion.

At action 204, the BS 105 transmits the QoS flows in the common DRB tothe UE 115. For example, where three QoS flows (as just an exemplaryvalue) are all mapped to the common DRB, those three QoS flows aretransmitted as part of that common DRB to the UE 115. One or moreaspects of information pertaining to CAPC may be included in thetransmission, for example in a header of the packet or a MAC CE, or RRCsignaling, etc.

At action 206, the UE 115 selects a CAPC for an UL transmission based ona rule. The UL transmission may be a configured grant transmission or adynamic grant transmission, with examples herein discussing configuredgrant transmission to illustrate examples. The rules may include a rulefrom those identified in the discussion relating to FIG. 1 above, e.g.,the QoS flows on a common DRB all are assigned to the common DRB by theBS 105 based on a shared QoS indicator (e.g., 5QI) and so the CAPC forthe common DRB is selected based on that assignment, or based on thehighest priority of the QoS flows in the common DRB, or based on thelowest priority of the QoS flows in the common DRB, or based on thepriority of a subset of the QoS flows identified by BS 105 signalingand/or of the QoS flows that share the same 5QI (identified, forexample, by a mapping between QoS flow identifier (QFI) and 5QI).

At action 208, the UE 115 uses the CAPC determined from action 206 inperforming a transmission for the common DRB (e.g., on configured grantresources) on the uplink to the BS 105. The value of the CAPC maydetermine the level of priority given for an LBT procedure on theuplink.

FIG. 3 is a block diagram of an exemplary UE 300 according toembodiments of the present disclosure. The UE 300 may be a UE 115discussed above in FIGS. 1 and 2. As shown, the UE 300 may include aprocessor 302, a memory 304, a CAPC control module 308, a transceiver310 including a modem subsystem 312 and a radio frequency (RF) unit 314,and one or more antennas 316. These elements may be in direct orindirect communication with each other, for example via one or morebuses.

The processor 302 may include a central processing unit (CPU), a digitalsignal processor (DSP), an application specific integrated circuit(ASIC), a controller, a field programmable gate array (FPGA) device,another hardware device, a firmware device, or any combination thereofconfigured to perform the operations described herein. The processor 302may also be implemented as a combination of computing devices, e.g., acombination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration.

The memory 304 may include a cache memory (e.g., a cache memory of theprocessor 302), random access memory (RAM), magnetoresistive RAM (MRAM),read-only memory (ROM), programmable read-only memory (PROM), erasableprogrammable read only memory (EPROM), electrically erasableprogrammable read only memory (EEPROM), flash memory, solid state memorydevice, hard disk drives, other forms of volatile and non-volatilememory, or a combination of different types of memory. In an embodiment,the memory 304 includes a non-transitory computer-readable medium. Thememory 304 may store, or have recorded thereon, instructions 306. Theinstructions 306 may include instructions that, when executed by theprocessor 302, cause the processor 302 to perform the operationsdescribed herein with reference to the UEs 115 in connection withembodiments of the present disclosure, for example, aspects of FIGS. 1-2and 5-8. Instructions 306 may also be referred to as program code. Theprogram code may be for causing a wireless communication device (orspecific component(s) of the wireless communication device) to performthese operations, for example by causing one or more processors (such asprocessor 302) to control or command the wireless communication device(or specific component(s) of the wireless communication device) to doso. The terms “instructions” and “code” should be interpreted broadly toinclude any type of computer-readable statement(s). For example, theterms “instructions” and “code” may refer to one or more programs,routines, sub-routines, functions, procedures, etc. “Instructions” and“code” may include a single computer-readable statement or manycomputer-readable statements.

The CAPC control module 308 may be implemented via hardware, software,or combinations thereof. For example, CAPC control module 308 may beimplemented as a processor, circuit, and/or instructions 306 stored inthe memory 304 and executed by the processor 302. In some examples, theCAPC control module 308 can be integrated within the modem subsystem312. For example, the CAPC control module 308 can be implemented by acombination of software components (e.g., executed by a DSP or a generalprocessor) and hardware components (e.g., logic gates and circuitry)within the modem subsystem 312.

The CAPC control module 308 may be used for various aspects of thepresent disclosure, for example, aspects of FIGS. 1-2 and 5-8. The CAPCcontrol module 308 is configured to communicate with other components ofthe UE 300 to transmit of one or more transmissions (e.g., configuredgrant) with a determined CAPC for a common DRB, receive one or more DLmessages such as QoS flows on a common DRB, determine a CAPC from thevarious QoS flows on the common DRB, determine whether a timer hasexpired, start a timer, cancel a timer, stop a timer, determine whethera transmission counter has reached a threshold, reset a transmissioncounter, restart a random access procedure, trigger RLF, and/or performother functionalities related to the CAPC determination procedures of aUE described in the present disclosure.

As shown, the transceiver 310 may include the modem subsystem 312 andthe RF unit 314. The transceiver 310 can be configured to communicatebi-directionally with other devices, such as the BSs 105. The modemsubsystem 312 may be configured to modulate and/or encode the data fromthe memory 304, and/or the CAPC control module 308 according to amodulation and coding scheme (MCS) (e.g., a low-density parity check(LDPC) coding scheme, a turbo coding scheme, a convolutional codingscheme, a digital beamforming scheme, etc.). The RF unit 314 may beconfigured to process (e.g., perform analog to digital conversion ordigital to analog conversion, etc.) modulated/encoded data (e.g., ULdata bursts, RRC messages, configured grant transmissions, ACK/NACKs forDL data bursts) from the modem subsystem 312 (on outbound transmissions)or of transmissions originating from another source such as a UE 115 ora BS 105. The RF unit 314 may be further configured to perform analogbeamforming in conjunction with the digital beamforming. Although shownas integrated together in transceiver 310, the modem subsystem 312 andthe RF unit 314 may be separate devices that are coupled together at theUE 300 to enable the UE 300 to communicate with other devices.

The RF unit 314 may provide the modulated and/or processed data (e.g.,data packets or, more generally, data messages that may contain one ormore data packets and other information) to the antennas 316 fortransmission to one or more other devices. The antennas 316 may furtherreceive data messages transmitted from other devices. The antennas 316may provide the received data messages for processing and/ordemodulation at the transceiver 310. The transceiver 310 may provide thedemodulated and decoded data (e.g., system information message(s), RACHmessage(s) (e.g., DL/UL scheduling grants, DL data bursts, RRC messages,ACK/NACK requests) to the CAPC control module 308 for processing. Theantennas 316 may include multiple antennas of similar or differentdesigns in order to sustain multiple transmission links. The RF unit 314may configure the antennas 316.

In an embodiment, the UE 300 can include multiple transceivers 310implementing different RATs (e.g., NR and LTE). In an embodiment, the UE300 can include a single transceiver 310 implementing multiple RATs(e.g., NR and LTE). In an embodiment, the transceiver 310 can includevarious components, where different combinations of components canimplement different RATs.

FIG. 4 is a block diagram of an exemplary BS 400 according toembodiments of the present disclosure. The BS 400 may be a BS 105 asdiscussed above in FIGS. 1 and 2. As shown, the BS 400 may include aprocessor 402, a memory 404, a CAPC control module 408, a transceiver410 including a modem subsystem 412 and a RF unit 414, and one or moreantennas 416. These elements may be in direct or indirect communicationwith each other, for example via one or more buses.

The processor 402 may have various features as a specific-typeprocessor. For example, these may include a CPU, a DSP, an ASIC, acontroller, a FPGA device, another hardware device, a firmware device,or any combination thereof configured to perform the operationsdescribed herein. The processor 402 may also be implemented as acombination of computing devices, e.g., a combination of a DSP and amicroprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration.

The memory 404 may include a cache memory (e.g., a cache memory of theprocessor 402), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, asolid state memory device, one or more hard disk drives, memristor-basedarrays, other forms of volatile and non-volatile memory, or acombination of different types of memory. In some embodiments, thememory 404 may include a non-transitory computer-readable medium. Thememory 404 may store instructions 406. The instructions 406 may includeinstructions that, when executed by the processor 402, cause theprocessor 402 to perform operations described herein, for example,aspects of FIGS. 1-2 and 5-8. Instructions 406 may also be referred toas code, which may be interpreted broadly to include any type ofcomputer-readable statement(s) as discussed above with respect to FIG.3.

The CAPC control module 408 may be implemented via hardware, software,or combinations thereof. For example, the CAPC control module 408 may beimplemented as a processor, circuit, and/or instructions 406 stored inthe memory 404 and executed by the processor 402. In some examples, theCAPC control module 408 can be integrated within the modem subsystem412. For example, the CAPC control module 408 can be implemented by acombination of software components (e.g., executed by a DSP or a generalprocessor) and hardware components (e.g., logic gates and circuitry)within the modem subsystem 412.

The CAPC control module 408 may be used for various aspects of thepresent disclosure, for example, aspects of FIGS. 1-2 and 5-8. The CAPCcontrol module 408 is configured to map QoS flows to a DRB (e.g.,multiple to a common DRB and/or to different DRBs), transmit orretransmit multiple QoS flows as part of the common DRB, transmit one ormore DL scheduling grants to a UE indicating DL resources (e.g.,time-frequency resources), transmit DL data to the UE, receive one ormore UL transmissions (e.g., configured grant) based on a CAPCdetermined for the common DRB with multiple QoS flows, etc.

The CAPC control module 408 is configured to communicate with othercomponents of the BS 400 to map QoS flows to DRB(s), transmit the DRBwith multiple QoS flows, receive one or more UL transmissions (e.g.,configured grant) based on CAPC determined for the common DRB havingmultiple QoS flows, determine whether a timer has expired, start atimer, cancel a timer, determine whether a transmission counter hasreached a threshold, reset a transmission counter, terminate a randomaccess procedure, and/or perform other functionalities related to theCAPC determination for DRBs having multiple QoS flows described in thepresent disclosure.

As shown, the transceiver 410 may include the modem subsystem 412 andthe RF unit 414. The transceiver 410 can be configured to communicatebi-directionally with other devices, such as the UEs 115 and/or 300and/or another core network element. The modem subsystem 412 may beconfigured to modulate and/or encode data according to a MCS (e.g., aLDPC coding scheme, a turbo coding scheme, a convolutional codingscheme, a digital beamforming scheme, etc.). The RF unit 414 may beconfigured to process (e.g., perform analog to digital conversion ordigital to analog conversion, etc.) modulated/encoded data (e.g., RRCmessages, DL data of multiple QoS flows mapped to the same DRB, etc.)from the modem subsystem 412 (on outbound transmissions) or oftransmissions originating from another source, such as a UE 115 or 300.The RF unit 414 may be further configured to perform analog beamformingin conjunction with the digital beamforming. Although shown asintegrated together in transceiver 410, the modem subsystem 412 and/orthe RF unit 414 may be separate devices that are coupled together at theBS 400 to enable the BS 400 to communicate with other devices.

The RF unit 414 may provide the modulated and/or processed data, (e.g.,data packets or, more generally, data messages that may contain one ormore data packets and other information) to the antennas 416 fortransmission to one or more other devices. This may include, forexample, communication with a camped UE 115 or 300 according toembodiments of the present disclosure. The antennas 416 may furtherreceive data messages transmitted from other devices and provide thereceived data messages for processing and/or demodulation at thetransceiver 410. The transceiver 410 may provide the demodulated anddecoded data (e.g., RRC messages, UL data of multiple QoS flows mappedto the same DRB, UL data, etc.) to the CAPC control module 408 forprocessing. The antennas 416 may include multiple antennas of similar ordifferent designs in order to sustain multiple transmission links.

In an embodiment, the BS 400 can include multiple transceivers 410implementing different RATs (e.g., NR and LTE). In an embodiment, the BS400 can include a single transceiver 410 implementing multiple RATs(e.g., NR and LTE). In an embodiment, the transceiver 410 can includevarious components, where different combinations of components canimplement different RATs.

Turning now to FIG. 5, a wireless communication network interaction 500is illustrated according to some embodiments of the present disclosure.For example, illustrated are some logical flows between a UPF 502, NB504, and UE 506. While there may be several NBs 504, and many UEs 506,to which embodiments of the present disclosure may apply, one of each isillustrated herein for simplicity of illustration and discussion. TheUPF 502 (user plane function) provides transport of data between the NB504 and the core network, and may represent a given gateway physicaldevice, or functionally represent operations performed at one ormultiple devices at one or more logical levels in the operationsaccording to embodiments of the present disclosure. The NB 504 may be anexample of the BS 115 and BS 400 as discussed herein. The UE 506 may bean example of the UE 115 and UE 300 as discussed herein. Additionaloperations and functions are performed between the three entitiesillustrated in FIG. 5 in addition to the CAPC determination aspectsdescribed herein.

Data packets arrive at the UPF 502 from one or more applicationsapplicable to the UE 506. These data packets are illustrated as datapackets 508 ₁ through 508 _(n). At the UPF 502, the packets 508 arefiltered by filter function 510 to map into QoS flows 512 ₁ through 512_(m). While illustrated as a single filter function 510, the filterfunction 510 may be any combination of filters implemented in softwareand/or hardware to accomplish the filtering result illustrated herein.Further to being mapped to QoS flows 512 ₁ through 512 _(m), the filterfunction 510 may apply marking to the packets of each mapped QoS flow512. The marking may be, for example, a different QFI for each QoS flow,for example based on a 5QI (or other representation to map a QoS levelto one or more QoS characteristics for the given packets/QoS flow). Asjust one example to illustrate embodiments of the present disclosure,the data packets 508 ₁ through 508 ₃ may be mapped by the filterfunction 510 to QoS flow 512 i, data packets 508 ₄ and 508 ₅ to QoS flow512 ₂, and data packet 508 _(n) (either one or multiple packets) to QoSflow 512 _(m).

The QoS flows 512 ₁ through 512 _(m) are sent to the NB 504. This may beaccomplished, for example, via a PDU session such as a single tunnelsession for all of the QoS flows of the PDU session. At the NB 504, theQoS flows 512 ₁ through 512 _(m) are mapped to one or more DRBs 516 ₁through 516 _(k) for transport to the UE 506 by mapping function 514.While illustrated as a single mapping function 514, the mapping function514 may be any combination of filters implemented in software and/orhardware to accomplish the mapping result illustrated herein. As justone example, the QoS flows 5121 and 5122 may be mapped to a first DRB516 ₁, and the QoS flow 512 _(m) may be mapped to a DRB 516 _(k). Asillustrated, therefore, there is a one-to-many relationship between theDRB 516 ₁ and the QoS flows 512 ₁ and 512 ₂ mapped to it.

The data is transmitted via the DRBs 516 ₁ through 516 _(k) to the UE506. Because of the one-to-many nature, however, a given DRB (such asDRB 516 ₁ in the illustrated example) may have multiple QoS flows withrespective QFIs. The UE 506 determine what CAPC to apply for the commonDRB on an uplink communication (e.g., configured grant), which may beaccomplished according to embodiments of the present disclosure. Thismay be accomplished, for example, by applying one or more rules asdiscussed above and further below.

An exemplary table format 600 for a mapping relationship according tosome embodiments of the present disclosure is illustrated in FIG. 6,which may provide a mapping between a CAPC and the various 5QIs. This isexemplary, and other mappings may be applicable as well, and benefitfrom, aspects of the present disclosure. As illustrated, a first column602 lists the different CAPCs. A second column lists the corresponding5QI(s) that correspond to a given CAPC. This correspondence isillustrated by rows 606. In the illustrated examples, therefore, CAPC 1may map the several 5QIs listed in the same row 606 as the CAPC 1, andso on through CAPC 4. In the illustrated example table 600, the lowernumbers have higher priority than the higher numbers.

FIG. 7 illustrates a flow diagram of a wireless communication method 700for determining and using a CAPC for an UL transmission (e.g.,configured grant) in situations where there may be multiple QoS flows ona common DRB, according to some embodiments of the present disclosure.Aspects of the method 700 can be executed by a wireless communicationdevice, such as the UEs 115, 300, and/or 506 utilizing one or morecomponents, such as the processor 302, the memory 304, the CAPC controlmodule 308, the transceiver 310, the modem 312, the one or more antennas316, and various combinations thereof. As illustrated, the method 700includes a number of enumerated steps, but embodiments of the method 700may include additional steps before, during, after, and in between theenumerated steps. Further, in some embodiments, one or more of theenumerated steps may be omitted or performed in a different order.

At decision block 702, if the BS 105 is configured to signal informationrelevant to the CAPC determination at the UE 115 outside of a given QoSflow (such as a QoS flow 512 illustrated in FIG. 5), such as adetermined CAPC for the common DRB itself, or 5QI, or subsetinformation, or other information for the UE 115 to apply with respectto one or more rules to determine the CAPC for the common DRB, then themethod 700 proceeds to decision block 704.

At decision block 704, if the BS 105 is configured in particular tosignal information regarding a subset of QoS flows to use in determininga CAPC for a common DRB transmission on the uplink, then the method 700proceeds to block 706.

At block 706, the UE 115 receives an indication of subset informationfrom the BS 105. The indication may include a list of the QoS flows thatcomprise the subset, or some smaller representation such as a short bitpattern that the UE 115 uses to look up, in a corresponding table, whatsubset the pattern identifies. The UE 115 may be configured to implementthe subset signaled by the BS 105 to determine the CAPC for the commonDRB based on the lowest or highest priority from among the QoS flowsidentified by the BS 105. The method 700 then proceeds from block 706 toblock 710 as described further below.

Returning to decision block 704, if the BS 105 is not configured tospecifically signal subset information, the method 700 instead proceedsto block 708. At block 708, the UE 115 receives QoS information from theBS 105. This may include different information depending on what rule(s)the UE 115 has been configured to implement in order to determine a CAPCfor the UL transmission. For example, where the rule includes the BS 105informing the UE 115 of what CAPC to use for the common DRB, the QoSinformation may be the determined CAPC. As another example, the QoSinformation may be 5QIs for the QoS flows (one or more of them). As yetanother example, the BS 105 may configure multiple mappings via RRCsignaling and dynamically change which mapping to use via MAC controlelement (CE), such as based on traffic patterns and traffic history ofthe QoS flows, which may be received as the QoS information at block708. The method 700 then proceeds to block 710 as will be discussedfurther below.

Returning to decision block 702, if the BS 105 is not configured tosignal information relevant to the CAPC determination at the UE 115outside of a given QoS flow, then the method 700 proceeds to block 710.

At block 710, the UE 105 receives QoS flows mapped to a common DRB fromthe BS 105 as part of a PDU session. FIG. 5 illustrates an example wheremultiple QoS flows 512 are mapped to a common DRB 516. With multiple QoSflows, the UE 105 applies one or more rules as discussed herein todetermine what CAPC to use for configured grant transmission.

At block 712, the UE 105 selects an UL CAPC based on a rule applied toQoS information of the QoS flows of the common DRB. For example, therule may be that different QoS flows carried on a common DRB are mappedby the BS 105 based on each QoS flow in the common DRB having the sameaccess priority (such as determined by the QoS flow's 5QI). Thus, therule at the UE 105 may be to apply the access priority for the groupedQoS flows in selecting the CAPC for the UL transmission (e.g.,configured grant).

As another example, the rule may be that the UE 115 select the CAPCbased on the lowest access priority, or the highest access priority, ofthe QoS flows on the common DRB. As another example, the rule may bethat the UE 115 select the CAPC based on the lowest or highest priorityfrom among a subset of QoS flows on the common DRB, where the subset issignaled by the BS 105 as discussed above with respect to block 706. Asanother example, the rule may be that the UE 115 select the CAPC basedon the priority of the greatest number of QoS flows on the common DRBthat have the same priority.

As another example, the BS 105 may determine the CAPC (or a value thatis determinative of CAPC) and signal that determination to the UE 115per the LCH, as well as updated such as when one or more QoS flows areadded or removed from the common DRB (for example, as discussed abovewith respect to block 708). As another example, the BS 105 may configuremultiple mappings via RRC signaling and dynamically change which mappingto use via MAC control element (CE), such as based on traffic patternsand traffic history of the QoS flows (as discussed with respect to block708 above).

In some embodiments, the UE 115 may receive one or more packetsbelonging to a QoS flow that the UE 115 has not received in the commonDRB. This may refer to reflective QoS. In such situations, the UE 115may update the access priority of the common DRB according to a knownrule (such as one of the above-noted rules). The UE 115 may receive theCAPC for this new QoS flow, such as in the received packet, in the SDAPheader, the PDCP header, MAC CE, RRC signaling, or PDCP control PDU(which may occur at block 708 as discussed above). This may instead, oradditionally, include the UE 115 receiving the 5QI for this QoS flow,such as in a received packet, or SDAP header, PDCP header, MAC CE, RRCsignaling, or PDCP control PDU (which may occur, again, as discussedabove with respect to block 708).

Further, when the BS 105 adds or removes QoS flows (one or multiple) forthe common DRB, the UE 105 may update the CAPC of the common DRB basedon the rule(s) in effect (such as from among those discussed above).Further, whenever the CAPC changes with respect to the common DRB for anUL transmission (e.g., configured grant) from the UE 115, the new CAPCmay be applied to subsequent UL transmissions for the commonDRB, oralternatively may begin application when received (e.g., toretransmissions). In general, when a new QoS flow is added, or when anexisting QoS flow is removed from the common DRB, the CAPC may besignaled to the UE 115 (or, alternatively to the CAPC, the 5QI for theQoS flow).

At block 714, the UE 115 uses the CAPC selected or determined from block712 to transmit UL data on the common DRB.

FIG. 8 illustrates a flow diagram of a wireless communication method 800for determining and using a CAPC for a transmission (e.g., configuredgrant) in situations where there may be multiple QoS flows on a commonDRB, according to some embodiments of the present disclosure. Aspects ofthe method 800 can be executed by a wireless communication device, suchas the BSs 105, 400, and/or 504 utilizing one or more components, suchas the processor 402, the memory 404, the CAPC control module 408, thetransceiver 410, the modem 412, the one or more antennas 416, andvarious combinations thereof. As illustrated, the method 800 includes anumber of enumerated steps, but embodiments of the method 800 mayinclude additional steps before, after, and in between the enumeratedsteps. In some embodiments, one or more of the enumerated steps may beomitted or performed in a different order.

At decision block 802, if the BS 105 is configured to signal informationrelevant to the CAPC determination at the UE 115 outside of a given QoSflow (such as a QoS flow 512 illustrated in FIG. 5), such as adetermined CAPC itself, or 5QI, or subset information, or otherinformation for the UE 115 to apply with respect to one or more rules,then the method 800 proceeds to decision block 804.

At decision block 804, if the BS 105 is configured in particular tosignal information regarding a subset of QoS flows to use in determininga CAPC for the common DRB for use on the uplink, then the method 800proceeds to block 806.

At block 806, the BS determines subset information to send to the UE115. The subset information may be signaled as an indication to the UE115, and may include a list of the QoS flows that comprise the subset,or some smaller representation such as a short bit pattern that the UE115 uses to look up, in a corresponding table, what subset the patternidentifies. The UE 115 may be configured to implement the subsetsignaled by the BS 105 to determine the CAPC for the common DRB based onthe lowest or highest priority from among the QoS flows identified bythe BS 105. The BS 105 transmits the subset information to the UE 115and the method 800 then proceeds from block 806 to block 810 asdescribed further below.

Returning to decision block 804, if the BS 105 is not configured tospecifically signal subset information, the method 800 instead proceedsto block 808. At block 808, the BS 105 transmits QoS information to theUE 115. This may include different information depending on what rule(s)the UE 115 has been configured to implement in order to determine a CAPCfor the common DRB for UL transmission (e.g., configured grant).Examples of the rules were discussed with respect to block 708 in FIG. 7above. The method 800 then proceeds to block 810 as will be discussedfurther below.

Returning to decision block 802, if the BS 105 is not configured tosignal information relevant to the CAPC determination for the common DRBat the UE 115 outside of a given QoS flow, then the method 800 proceedsto block 810.

At block 810, the BS 105 aggregates (maps) the QoS flows into one ormore DRBs. FIG. 5 illustrates an example where multiple QoS flows 512are mapped to a common DRB 516.

At block 812, the BS 105 transmits the QoS flows of the common DRB tothe UE 115 as part of a PDU session. With multiple QoS flows, the UE 105applies one or more rules as discussed herein to determine what CAPC touse for the common DRB on the UL for UL transmission (e.g., configuredgrant).

At block 814, the BS 105 receives an UL transmission (e.g., configuredgrant) from the UE 105 with a CAPC for the common DRB on the ULdetermined based on the rules, such as one of those discussed above withrespect to FIG. 7.

Information and signals may be represented using any of a variety ofdifferent technologies and techniques. For example, data, instructions,commands, information, signals, bits, symbols, and chips that may bereferenced throughout the above description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection withthe disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, an ASIC, an FPGA or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor may be a microprocessor,but in the alternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices (e.g., a combinationof a DSP and a microprocessor, multiple microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described above can be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations. Also, as used herein, including in the claims, “or” as usedin a list of items (for example, a list of items prefaced by a phrasesuch as “at least one of” or “one or more of”) indicates an inclusivelist such that, for example, a list of [at least one of A, B, or C]means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

Further embodiments of the present disclosure include a non-transitorycomputer-readable medium having program code recorded thereon, theprogram code comprising code for causing a user equipment (UE) toreceive, from a base station (BS), a plurality of downlink data packetscomprising a corresponding plurality of quality of service flows (QoSflows), each the plurality of QoS flows being mapped to a common dataradio bearer (DRB); code for causing the UE to select a channel accesspriority class (CAPC) for the common DRB for transmitting an UL datapacket based on a rule applied to the plurality of QoS flows mapped tothe common DRB; and code for causing the UE to transmit, to the BS, theuplink data packet with the selected CAPC.

The non-transitory computer-readable medium may also include wherein theplurality of QoS flows mapped to the common DRB comprise a correspondingplurality of CAPCs. The non-transitory computer-readable medium may alsoinclude wherein the plurality of QoS flows are mapped to the common DRBbased on the corresponding plurality of CAPCs being the same among theplurality of QoS flows, wherein the code for causing the selectingfurther comprises code for causing the UE to select the CAPC for thecommon DRB based on the same CAPC. The non-transitory computer-readablemedium may also include wherein a first CAPC from among the plurality ofCAPCs comprises a lower access priority than a second CAPC from amongthe plurality of CAPCs, wherein the code for causing the selectingfurther comprises code for causing the UE to select the first CAPC basedon the first CAPC comprising the lower access priority. Thenon-transitory computer-readable medium may also include wherein a firstCAPC from among the plurality of CAPCs comprises a higher accesspriority than a second CAPC from among the plurality of CAPCs, whereinthe code for causing the selecting further comprises code for causingthe UE to select the first CAPC based on the first CAPC comprising thehigher access priority. The non-transitory computer-readable medium mayalso include wherein the code for causing the selecting furthercomprises code for causing the UE to receive, from the BS, anidentification of a subset of QoS flows from among the plurality of QoSflows. The non-transitory computer-readable medium may also include codefor causing the UE to select the CAPC based on a QoS flow from thesubset having a first CAPC comprising a lower access priority than CAPCscorresponding to a remainder of the subset. The non-transitorycomputer-readable medium may also include code for causing the UE toselect the CAPC based on a QoS flow from the subset having a first CAPCcomprising a higher access priority than CAPCs corresponding to aremainder of the subset. The non-transitory computer-readable medium mayalso include wherein the code for causing the selecting furthercomprises code for causing the UE to identify a first subset of QoSflows from among the plurality of QoS flows having first common CAPC;code for causing the UE to identify a second subset of QoS flows fromamong the plurality of QoS flows having a second common CAPC, the secondcommon CAPC being different from the first common CAPC; and code forcausing the UE to select the CAPC based on the first common CAPC inresponse to the first subset of QoS flows being greater than the secondsubset of QoS flows. The non-transitory computer-readable medium mayalso include wherein the code for causing the selecting furthercomprises code for causing the UE to receive, from the BS, a selectionfor the CAPC; and code for causing the UE to implement the receivedselection as the CAPC. The non-transitory computer-readable medium mayalso include code for causing the UE to receive, from the BS, adetermined CAPC in response to a new QoS flow being added to theplurality of QoS flows. The non-transitory computer-readable medium mayalso include code for causing the UE to receive, from the BS, adetermined QoS indicator in response to a new QoS flow being added tothe plurality of QoS flows; and code for causing the UE to determine theCAPC based on the determined QoS indicator. The non-transitorycomputer-readable medium may also include wherein the plurality of QoSflows comprises a new QoS flow not used already for the common DRB, thecode further comprising code for causing the UE to update the CAPC forthe common DRB based on the rule. The non-transitory computer-readablemedium may also include wherein the code for causing the transmittingfurther comprises code for causing the UE to transmit, to the BS, the ULdata packet with the selected CAPC during a configured grant.

Further embodiments of the present disclosure include a non-transitorycomputer-readable medium having program code recorded thereon, theprogram code comprising code for causing a base station (BS) to map aplurality of downlink data packets comprising a corresponding pluralityof quality of service flows (QoS flows) to a common data radio bearer(DRB); code for causing the BS to transmit, to a user equipment (UE),the plurality of downlink data packets on the common DRB; and code forcausing the BS to receive, from the UE, an uplink (UL) data packet onthe common DRB having a channel access priority class (CAPC) selectedbased on a rule applied to the plurality of QoS flows mapped to thecommon DRB.

The non-transitory computer-readable medium may also include wherein theplurality of QoS flows mapped to the common DRB comprise a correspondingplurality of CAPCs. The non-transitory computer-readable medium may alsoinclude wherein the plurality of QoS flows are mapped to the common DRBbased on the corresponding plurality of CAPCs being the same among theplurality of QoS flows, the CAPC for the common DRB being selected basedon the same CAPC. The non-transitory computer-readable medium may alsoinclude wherein a first CAPC from among the plurality of CAPCs comprisesa lower access priority than a second CAPC from among the plurality ofCAPCs, the first CAPC being selected based on the first CAPC comprisingthe lower access priority. The non-transitory computer-readable mediummay also include wherein a first CAPC from among the plurality of CAPCscomprises a higher access priority than a second CAPC from among theplurality of CAPCs, the first CAPC being based on the first CAPCcomprising the higher access priority. The non-transitorycomputer-readable medium may also include code for causing the BS totransmit, to the UE, an identification of a subset of QoS flows fromamong the plurality of QoS flows. The non-transitory computer-readablemedium may also include the CAPC being based on a QoS flow from thesubset having a first CAPC comprising a lower access priority than CAPCscorresponding to a remainder of the subset. The non-transitorycomputer-readable medium may also include the UL CAPC being based on aQoS flow from the subset having a first CAPC comprising a higher accesspriority than CAPCs corresponding to a remainder of the subset. Thenon-transitory computer-readable medium may also include the CAPC beingbased on a first subset of QoS flows from among the plurality of QoSflows being greater than a second subset of QoS flows from among theplurality of QoS flows, wherein the first subset of QoS flows has afirst common CAPC and the second subset of QoS flows has a second commonCAPC different from the first common CAPC. The non-transitorycomputer-readable medium may also include code for causing the BS toselect the CAPC for the UE; and code for causing the BS to transmit, tothe UE, the selection to the UE to implement. The non-transitorycomputer-readable medium may also include code for causing the BS totransmit, to the UE, a determined CAPC in response to a new QoS flowbeing added to the plurality of QoS flows. The non-transitorycomputer-readable medium may also include code for causing the BS totransmit, to the UE, a determined QoS indicator in response to a new QoSflow being added to the plurality of QoS flows. The non-transitorycomputer-readable medium may also include wherein the code for thereceiving further comprises code for causing the BS to receive, from theUE, the UL data packet with the selected CAPC during a configured grant.

Further embodiments of the present disclosure include a user equipmentincluding means for receiving, by the user equipment (UE) from a basestation (BS), a plurality of downlink data packets comprising acorresponding plurality of quality of service flows (QoS flows), eachthe plurality of QoS flows being mapped to a common data radio bearer(DRB); means for selecting a channel access priority class (CAPC) forthe common DRB for transmitting an UL data packet based on a ruleapplied to the plurality of QoS flows mapped to the common DRB; andmeans for transmitting, to the BS, the uplink data packet with theselected CAPC.

The user equipment may also include wherein the plurality of QoS flowsmapped to the common DRB comprise a corresponding plurality of CAPCs.The user equipment may also include wherein the plurality of QoS flowsare mapped to the common DRB based on the corresponding plurality ofCAPCs being the same among the plurality of QoS flows, the means forselecting further comprising means for selecting the CAPC for the commonDRB based on the same CAPC. The user equipment may also include whereina first CAPC from among the plurality of CAPCs comprises a lower accesspriority than a second CAPC from among the plurality of CAPCs, the meansfor selecting further comprising means for selecting the first CAPCbased on the first CAPC comprising the lower access priority. The userequipment may also include wherein a first CAPC from among the pluralityof CAPCs comprises a higher access priority than a second CAPC fromamong the plurality of CAPCs, the means for selecting further comprisingmeans for selecting the first CAPC based on the first CAPC comprisingthe higher access priority. The user equipment may also include whereinthe means for selecting further comprises means for receiving, from theBS, an identification of a subset of QoS flows from among the pluralityof QoS flows. The user equipment may also include means for selectingthe CAPC based on a QoS flow from the subset having a first CAPCcomprising a lower access priority than CAPCs corresponding to aremainder of the subset. The user equipment may also include means forselecting the CAPC based on a QoS flow from the subset having a firstCAPC comprising a higher access priority than CAPCs corresponding to aremainder of the subset. The user equipment may also include wherein themeans for selecting further comprises means for identifying a firstsubset of QoS flows from among the plurality of QoS flows having firstcommon CAPC; means for identifying a second subset of QoS flows fromamong the plurality of QoS flows having a second common CAPC, the secondcommon CAPC being different from the first common CAPC; and means forselecting the CAPC based on the first common CAPC in response to thefirst subset of QoS flows being greater than the second subset of QoSflows. The user equipment may also include wherein the means forselecting further comprises means for receiving, from the BS, aselection for the CAPC; and means for implementing the receivedselection as the CAPC. The user equipment may also include means forreceiving, from the BS, a determined CAPC in response to a new QoS flowbeing added to the plurality of QoS flows. The user equipment may alsoinclude means for receiving, from the BS, a determined QoS indicator inresponse to a new QoS flow being added to the plurality of QoS flows;and means for determining the CAPC based on the determined QoSindicator. The user equipment may also include wherein the plurality ofQoS flows comprises a new QoS flow not used already for the common DRB,further comprising means for updating the CAPC for the common DRB basedon the rule. The user equipment may also include wherein thetransmitting further comprises means for transmitting, to the BS, the ULdata packet with the selected CAPC during a configured grant.

Further embodiments of the present disclosure include a base stationincluding means for mapping, by the base station (BS), a plurality ofdownlink data packets comprising a corresponding plurality of quality ofservice flows (QoS flows) to a common data radio bearer (DRB); means fortransmitting, to a user equipment (UE), the plurality of downlink datapackets on the common DRB; and means for receiving, from the UE, anuplink (UL) data packet on the common DRB having a channel accesspriority class (CAPC) selected based on a rule applied to the pluralityof QoS flows mapped to the common DRB.

The base station may also include wherein the plurality of QoS flowsmapped to the common DRB comprise a corresponding plurality of CAPCs.The base station may also include wherein the plurality of QoS flows aremapped to the common DRB based on the corresponding plurality of CAPCsbeing the same among the plurality of QoS flows, the CAPC for the commonDRB being selected based on the same CAPC. The base station may alsoinclude wherein a first CAPC from among the plurality of CAPCs comprisesa lower access priority than a second CAPC from among the plurality ofCAPCs, the first CAPC being selected based on the first CAPC comprisingthe lower access priority. The base station may also include wherein afirst CAPC from among the plurality of CAPCs comprises a higher accesspriority than a second CAPC from among the plurality of CAPCs, the firstCAPC being based on the first CAPC comprising the higher accesspriority. The base station may also include means for transmitting, tothe UE, an identification of a subset of QoS flows from among theplurality of QoS flows. The base station may also include the CAPC beingbased on a QoS flow from the subset having a first CAPC comprising alower access priority than CAPCs corresponding to a remainder of thesubset. The base station may also include the UL CAPC being based on aQoS flow from the subset having a first CAPC comprising a higher accesspriority than CAPCs corresponding to a remainder of the subset. The basestation may also include the CAPC being based on a first subset of QoSflows from among the plurality of QoS flows being greater than a secondsubset of QoS flows from among the plurality of QoS flows, wherein thefirst subset of QoS flows has a first common CAPC and the second subsetof QoS flows has a second common CAPC different from the first commonCAPC. The base station may also include means for selecting the CAPC forthe UE; and means for transmitting, to the UE, the selection to the UEto implement. The base station may also include means for transmitting,to the UE, a determined CAPC in response to a new QoS flow being addedto the plurality of QoS flows. The base station may also include meansfor transmitting, to the UE, a determined QoS indicator in response to anew QoS flow being added to the plurality of QoS flows. The base stationmay also include wherein the means for receiving further comprises meansfor receiving, from the UE, the UL data packet with the selected CAPCduring a configured grant.

As those of some skill in this art will by now appreciate and dependingon the particular application at hand, many modifications, substitutionsand variations can be made in and to the materials, apparatus,configurations and methods of use of the devices of the presentdisclosure without departing from the spirit and scope thereof. In lightof this, the scope of the present disclosure should not be limited tothat of the particular embodiments illustrated and described herein, asthey are merely by way of some examples thereof, but rather, should befully commensurate with that of the claims appended hereafter and theirfunctional equivalents.

What is claimed is:
 1. A method of wireless communication performed by auser equipment (UE), comprising: receiving a plurality of data packetsvia a common data radio bearer (DRB), the common DRB comprising aplurality of mapped quality of service flows (QoS flows); implementing achannel access priority class (CAPC) for the common DRB for transmittinga response data packet based on a rule applied to the plurality ofmapped QoS flows; and transmitting the response data packet with theimplemented CAPC.
 2. The method of claim 1, further comprising:receiving the CAPC for the common DRB, the CAPC determined by a separatewireless communications device per a logical channel (LCH) correspondingto each DRB.
 3. The method of claim 2, wherein the plurality of mappedQoS flows are mapped to the common DRB based on a correspondingplurality of CAPCs being the same among the plurality of mapped QoSflows, the rule comprising implementing the CAPC for the common DRBbased on the same CAPC.
 4. The method of claim 2, wherein a first CAPCfrom among a plurality of CAPCs corresponding to the plurality of mappedQoS flows comprises a lower access priority than a second CAPC fromamong the plurality of CAPCs, the rule comprising implementing the firstCAPC based on the first CAPC comprising the lower access priority. 5.The method of claim 2, wherein a first CAPC from among a plurality ofCAPCs corresponding to the plurality of mapped QoS flows comprises ahigher access priority than a second CAPC from among the plurality ofCAPCs, the rule comprising implementing the first CAPC based on thefirst CAPC comprising the higher access priority.
 6. The method of claim2, wherein the rule comprises implementing the CAPC based on a QoS flowfrom a subset of QoS flows, the subset of QoS flows being from among theplurality of mapped QoS flows.
 7. The method of claim 2, wherein therule comprises implementing the CAPC based on a first common CAPCidentified from a first subset of QoS flows from among the plurality ofmapped QoS flows, the first subset of QoS flows being greater than asecond subset of QoS flows having a second common CAPC different fromthe first common CAPC.
 8. The method of claim 2, further comprising:receiving an update to the CAPC in response to a new QoS flow beingadded to the plurality of QoS flows.
 9. A method of wirelesscommunication performed by a network node, comprising: selecting, basedon a rule applied to a plurality of quality of service (QoS) flowsmapped to a common data radio bearer (DRB), a channel access priorityclass (CAPC) for a user equipment (UE) to implement for a response datapacket; transmitting the selected CAPC; transmitting a plurality of datapackets via the common DRB, the common DRB comprising the plurality ofQoS flows; and receiving the response data packet on the common DRBhaving the selected CAPC.
 10. The method of claim 9, wherein theselecting further comprises: determining the selected CAPC for thecommon DRB per a logical channel (LCH) corresponding to each DRB. 11.The method of claim 10, wherein: the plurality of QoS flows are mappedto the common DRB based on a plurality of CAPCs corresponding to theplurality of QoS flows being the same among the plurality of QoS flows,and the selecting the CAPC for the common DRB is based on the same CAPC.12. The method of claim 10, wherein: a first CAPC from among a pluralityof CAPCs corresponding to the plurality of QoS flows comprises a loweraccess priority than a second CAPC from among the plurality of CAPCs,and the selecting the CAPC comprises selecting the first CAPC based onthe first CAPC comprising the lower access priority.
 13. The method ofclaim 10, wherein: a first CAPC from among a plurality of CAPCscorresponding to the plurality of QoS flows comprises a higher accesspriority than a second CAPC from among the plurality of CAPCs, and theselecting the CAPC comprises selecting the first CAPC based on the firstCAPC comprising the higher access priority.
 14. The method of claim 10,wherein the selecting further comprises: selecting the selected CAPCbased on a QoS flow from a subset of QoS flows, the subset of QoS flowsbeing from among the plurality of QoS flows.
 15. The method of claim 10,wherein the selected CAPC is based on a first subset of QoS flows fromamong the plurality of QoS flows being greater than a second subset ofQoS flows from among the plurality of QoS flows, wherein the firstsubset of QoS flows has a first common CAPC and the second subset of QoSflows has a second common CAPC different from the first common CAPC. 16.An apparatus for wireless communication, comprising: a transceiverconfigured to receive a plurality of data packets via a common dataradio bearer (DRB), the common DRB comprising a plurality of mappedquality of service flows (QoS flows); and a processor configured toimplement a channel access priority class (CAPC) for the common DRB totransmit a response data packet based on a rule applied to the pluralityof mapped QoS, wherein the transceiver is further configured to transmitthe response data packet with the implemented CAPC.
 17. The apparatus ofclaim 16, wherein the transceiver is further configured to receive theCAPC for the common DRB, the CAPC determined by a separate wirelesscommunications device per a logical channel (LCH) corresponding to eachDRB.
 18. The apparatus of claim 17, wherein the plurality of mapped QoSflows are mapped to the common DRB based on a corresponding plurality ofCAPCs being the same among the plurality of mapped QoS flows, the rulecomprising implementing the CAPC for the common DRB based on the sameCAPC.
 19. The apparatus of claim 17, wherein a first CAPC from among aplurality of CAPCs corresponding to the plurality of mapped QoS flowscomprises a lower access priority than a second CAPC from among theplurality of CAPCs, the rule comprising implementing the first CAPCbased on the first CAPC comprising the lower access priority.
 20. Theapparatus of claim 17, wherein a first CAPC from among a plurality ofCAPCs corresponding to the plurality of mapped QoS flows comprises ahigher access priority than a second CAPC from among the plurality ofCAPCs, the rule comprising implementing the first CAPC based on thefirst CAPC comprising the higher access priority.
 21. The apparatus ofclaim 17, wherein the rule comprises implementing the CAPC based on aQoS flow from a subset of QoS flows, the subset of QoS flows being fromamong the plurality of mapped QoS flows.
 22. The apparatus of claim 17,wherein the rule comprises implementing the CAPC based on a first commonCAPC identified from a first subset of QoS flows from among theplurality of mapped QoS flows, the first subset of QoS flows beinggreater than a second subset of QoS flows having a second common CAPCdifferent from the first common CAPC.
 23. The apparatus of claim 17,wherein the transceiver is further configured to: receive an updated tothe implemented CAPC in response to a new QoS flow being added to theplurality of QoS flows.
 24. An apparatus for wireless communication,comprising: a processor configured to select, based on a rule applied toa plurality of quality of service (QoS) flows mapped to a common dataradio bearer (DRB), a channel access priority class (CAPC) for a userequipment (UE) to implement for a response data packet; and atransceiver configured to: transmit the selected CAPC; transmit aplurality of data packets via the common DRB, the common DRB comprisingthe plurality of QoS flows; and receive the response data packet on thecommon DRB having the selected CAPC.
 25. The apparatus of claim 24,wherein the processor is further configured, for the selection, to:determine the selected CAPC for the common DRB per a logical channel(LCH) corresponding to each DRB.
 26. The apparatus of claim 25, wherein:the plurality of QoS flows are mapped to the common DRB based on acorresponding plurality of CAPCs corresponding to the plurality of QoSflows being the same among the plurality of QoS flows, and the processoris configured to select the CAPC for the common DRB based on the sameCAPC.
 27. The apparatus of claim 25, wherein: a first CAPC from among aplurality of CAPCs corresponding to the plurality of QoS flows comprisesa lower access priority than a second CAPC from among the plurality ofCAPCs, and the processor is configured to select the first CAPC based onthe first CAPC comprising the lower access priority.
 28. The apparatusof claim 25, wherein: a first CAPC from among a plurality of CAPCscorresponding to the plurality of QoS flows comprises a higher accesspriority than a second CAPC from among the plurality of CAPCs, and thetransceiver is further configured to select the first CAPC based on thefirst CAPC comprising the higher access priority.
 29. The apparatus ofclaim 25, wherein the processor is further configured to: select theCAPC based on a QoS flow from a subset of QoS flows, the subset of QoSflows being from among the plurality of QoS flows.
 30. The apparatus ofclaim 25, where the selected CAPC is based on a first subset of QoSflows from among the plurality of QoS flows being greater than a secondsubset of QoS flows from among the plurality of QoS flows, wherein thefirst subset of QoS flows has a first common CAPC and the second subsetof QoS flows has a second common CAPC different from the first commonCAPC.